Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01f72c963470f858db7feea4fea0e16a07ce0a690e2cd1bc628919d7a2288ab2

Tx prefix hash: 3a186c2a65324ace44d29ebc8a9bc0651504b11280428143cd9683c161f8ef3a
Tx public key: 35699c1312c64174ec42bd2dd0e4006a31ee1d2ef7fc2e3d2d453e075d639207
Timestamp: 1740059110 Timestamp [UTC]: 2025-02-20 13:45:10 Age [y:d:h:m:s]: 00:358:16:22:12
Block: 1223387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254039 RingCT/type: yes/0
Extra: 0135699c1312c64174ec42bd2dd0e4006a31ee1d2ef7fc2e3d2d453e075d639207021100000001e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a5103ebbda9091b420ce3eee84b6d7baceca0fc86a3f538467fe5a561b24cec7 0.000600000000 1710244 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": 1223397, "vin": [ { "gen": { "height": 1223387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5103ebbda9091b420ce3eee84b6d7baceca0fc86a3f538467fe5a561b24cec7" } } ], "extra": [ 1, 53, 105, 156, 19, 18, 198, 65, 116, 236, 66, 189, 45, 208, 228, 0, 106, 49, 238, 29, 46, 247, 252, 46, 61, 45, 69, 62, 7, 93, 99, 146, 7, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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) | dinastycoin version: tesla-369