Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97247ce1df3d85e484674cf5dae4c5fee6f83857fd0e31b662ce02ee31389bce

Tx prefix hash: 6bccba59e28f5cf7a39511dcce0eff4d9139125ee48c78d15babb566f3852d31
Tx public key: 657c6ec25bd47c52a39f3ea0107b1909f6a49b25b3c10f11af224c666e017ddd
Timestamp: 1749850915 Timestamp [UCT]: 2025-06-13 21:41:55 Age [y:d:h:m:s]: 00:206:21:50:55
Block: 1304391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145713 RingCT/type: yes/0
Extra: 01657c6ec25bd47c52a39f3ea0107b1909f6a49b25b3c10f11af224c666e017ddd021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e10df2f62efe7bd93a3e6366bf5f666d02ca286d2f44213fa721d51ab9ef9a4d 0.600000000000 1791980 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 dinasty-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": 1304401, "vin": [ { "gen": { "height": 1304391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e10df2f62efe7bd93a3e6366bf5f666d02ca286d2f44213fa721d51ab9ef9a4d" } } ], "extra": [ 1, 101, 124, 110, 194, 91, 212, 124, 82, 163, 159, 62, 160, 16, 123, 25, 9, 246, 164, 155, 37, 179, 193, 15, 17, 175, 34, 76, 102, 110, 1, 125, 221, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8