Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc2801aed14f7d2b949e7a75ab1e833ee3cb8c1b6053596b74f5f21ffd89c1e1

Tx prefix hash: dcd690121ccc4e929faa9e611a930faa94ad124fa7ae8ea10eec99c5554b3a81
Tx public key: 1f1276221ab1ae8a8c97d03f141ea847e5c830f5a635594778d43854aa5d3ec3
Timestamp: 1711333571 Timestamp [UTC]: 2024-03-25 02:26:11 Age [y:d:h:m:s]: 02:052:00:41:38
Block: 985728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 549096 RingCT/type: yes/0
Extra: 011f1276221ab1ae8a8c97d03f141ea847e5c830f5a635594778d43854aa5d3ec302110000000152d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 045d163a0fd0e29e9ec0a9d1dfa5ebcd79966b4fa05c1ff1e8546e32073cdec7 0.000600000000 1445945 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": 985738, "vin": [ { "gen": { "height": 985728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "045d163a0fd0e29e9ec0a9d1dfa5ebcd79966b4fa05c1ff1e8546e32073cdec7" } } ], "extra": [ 1, 31, 18, 118, 34, 26, 177, 174, 138, 140, 151, 208, 63, 20, 30, 168, 71, 229, 200, 48, 245, 166, 53, 89, 71, 120, 212, 56, 84, 170, 93, 62, 195, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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: