Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a8c372b2d7bdcc35c19dfa9ad9702cf36f6a79cbfe8581719d1f386a881249b

Tx prefix hash: 1a14212595b22e89a5dc6021488759165680d02f0342b89708c30348339c2558
Tx public key: fa87876f59f613c6dce4ed19ba0e7be4cf28e761a433fd3eeb33d4c198b5fa8e
Timestamp: 1737086172 Timestamp [UCT]: 2025-01-17 03:56:12 Age [y:d:h:m:s]: 00:156:14:11:19
Block: 1199050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111562 RingCT/type: yes/0
Extra: 01fa87876f59f613c6dce4ed19ba0e7be4cf28e761a433fd3eeb33d4c198b5fa8e021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fd202989ce62cde29f7a7593a4a2ceca484e0dabdc2061c925d8c25697713e7 0.600000000000 1685679 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": 1199060, "vin": [ { "gen": { "height": 1199050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fd202989ce62cde29f7a7593a4a2ceca484e0dabdc2061c925d8c25697713e7" } } ], "extra": [ 1, 250, 135, 135, 111, 89, 246, 19, 198, 220, 228, 237, 25, 186, 14, 123, 228, 207, 40, 231, 97, 164, 51, 253, 62, 235, 51, 212, 193, 152, 181, 250, 142, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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