Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b56f8b51250963ad7e1e4fdc90c1d64123ee1c15c55c9aedd25d0d8214cdccdb

Tx prefix hash: cbc70da050a9851cfd340a2e53e1d71c60b5ec30c77b7b254c08cd82f41fa769
Tx public key: 601d915a785945447e2338762034b7ad83d0e103267fc64b0a1476184a220166
Timestamp: 1742043301 Timestamp [UTC]: 2025-03-15 12:55:01 Age [y:d:h:m:s]: 01:249:00:13:25
Block: 1239849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442060 RingCT/type: yes/0
Extra: 01601d915a785945447e2338762034b7ad83d0e103267fc64b0a1476184a220166021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2277cf4475c092c4f1bad62640228c7ceba9b796996b42dd2a4b8836e629b241 0.000600000000 1726814 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": 1239859, "vin": [ { "gen": { "height": 1239849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2277cf4475c092c4f1bad62640228c7ceba9b796996b42dd2a4b8836e629b241" } } ], "extra": [ 1, 96, 29, 145, 90, 120, 89, 69, 68, 126, 35, 56, 118, 32, 52, 183, 173, 131, 208, 225, 3, 38, 127, 198, 75, 10, 20, 118, 24, 74, 34, 1, 102, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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: