Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: c2cbd527c04fd40afdba4989ebc7646f5adf4c5681a586bb4d2b2933612ceb48

Tx prefix hash: a7ca8aef11faec6c34ec8b840ad40d70188e653f74038c7b40e3249156e210f0
Tx public key: 4563a1f074bd302ff34bc69a5ed5e84327f4b5629930cedfa120f28dc4a0e282
Timestamp: 1743794614 Timestamp [UTC]: 2025-04-04 19:23:34 Age [y:d:h:m:s]: 01:041:06:25:22
Block: 1254323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280456 RingCT/type: yes/0
Extra: 014563a1f074bd302ff34bc69a5ed5e84327f4b5629930cedfa120f28dc4a0e282021100000004a2ed016b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cbd4d52f04a27b3bbb75159c3a66ea28c59b53007907b696db2bb641320054e2 0.000600000000 1741404 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1254333, "vin": [ { "gen": { "height": 1254323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbd4d52f04a27b3bbb75159c3a66ea28c59b53007907b696db2bb641320054e2" } } ], "extra": [ 1, 69, 99, 161, 240, 116, 189, 48, 47, 243, 75, 198, 154, 94, 213, 232, 67, 39, 244, 181, 98, 153, 48, 206, 223, 161, 32, 242, 141, 196, 160, 226, 130, 2, 17, 0, 0, 0, 4, 162, 237, 1, 107, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: