Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1503523a690e25afa973010c303a8ee0b716b6d3d47e811b8f27df190e228361

Tx prefix hash: f035b9094698d582f45af1745bd97f833c93cf711447c12a8335a5d5f67a2288
Tx public key: e37d7ec3240d32137b5e2c0f07cba1974826e626c98791b3b19c14c65011fc5c
Timestamp: 1754327759 Timestamp [UCT]: 2025-08-04 17:15:59 Age [y:d:h:m:s]: 00:095:14:41:41
Block: 1340231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67284 RingCT/type: yes/0
Extra: 01e37d7ec3240d32137b5e2c0f07cba1974826e626c98791b3b19c14c65011fc5c0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2aae9ffc5433f0967d1d8b472458c93c6b0af89015f5d9ef60715f010dc36877 0.600000000000 1828048 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": 1340241, "vin": [ { "gen": { "height": 1340231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2aae9ffc5433f0967d1d8b472458c93c6b0af89015f5d9ef60715f010dc36877" } } ], "extra": [ 1, 227, 125, 126, 195, 36, 13, 50, 19, 123, 94, 44, 15, 7, 203, 161, 151, 72, 38, 230, 38, 201, 135, 145, 179, 177, 156, 20, 198, 80, 17, 252, 92, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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