Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfb8e322a3073ba44607c3ab8906be6c0d504af12e2f4dab3c4b849e4f61a8d1

Tx prefix hash: bda0e9e660c92c839fdab3c530b72edbdacf2292493506ef97e2087ca0daeffe
Tx public key: c8a4b726e4bc14df2d7901d247833a964de9e381dc8dcffa03ab804372b62de1
Timestamp: 1775051213 Timestamp [UTC]: 2026-04-01 13:46:53 Age [y:d:h:m:s]: 00:227:06:55:30
Block: 1510548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167844 RingCT/type: yes/0
Extra: 01c8a4b726e4bc14df2d7901d247833a964de9e381dc8dcffa03ab804372b62de1021100000005e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1cba6700ffd602fb97412902cb479d18d0de5b50ffcad9a9c9988efb9b36ee40 0.000600000000 2000332 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": 1510558, "vin": [ { "gen": { "height": 1510548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cba6700ffd602fb97412902cb479d18d0de5b50ffcad9a9c9988efb9b36ee40" } } ], "extra": [ 1, 200, 164, 183, 38, 228, 188, 20, 223, 45, 121, 1, 210, 71, 131, 58, 150, 77, 233, 227, 129, 220, 141, 207, 250, 3, 171, 128, 67, 114, 182, 45, 225, 2, 17, 0, 0, 0, 5, 227, 215, 220, 159, 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: