Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d37fd8d19bd3badd8a2f5c93264f9bfcbbab5417ab6ca37eac2542c7cf8d0fbb

Tx prefix hash: bc436f58076bffe66671048df2c4b17791546de8fda331ae3e81340e941fca2e
Tx public key: 8a86d36d8d051599581ec3c5d1313d2d025daf9359467968382a3442933ffe8c
Timestamp: 1742157389 Timestamp [UCT]: 2025-03-16 20:36:29 Age [y:d:h:m:s]: 00:291:08:38:06
Block: 1240804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206005 RingCT/type: yes/0
Extra: 018a86d36d8d051599581ec3c5d1313d2d025daf9359467968382a3442933ffe8c02110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88b6306a2d7d1dc2eb68c199137df81fbb16caf6463a5ca3c38950f3332d7b9d 0.600000000000 1727777 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": 1240814, "vin": [ { "gen": { "height": 1240804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88b6306a2d7d1dc2eb68c199137df81fbb16caf6463a5ca3c38950f3332d7b9d" } } ], "extra": [ 1, 138, 134, 211, 109, 141, 5, 21, 153, 88, 30, 195, 197, 209, 49, 61, 45, 2, 93, 175, 147, 89, 70, 121, 104, 56, 42, 52, 66, 147, 63, 254, 140, 2, 17, 0, 0, 0, 14, 31, 10, 83, 235, 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