Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2969d898049c11b842aa06c5cce4f833405dbe66e0bfa8e8234f8231f2211179

Tx prefix hash: ffe94652d10e48766fa0febaed09b13c8f25b5ef72bff2af15401b62d03fd3bd
Tx public key: 59c9d5f1891e8df7a9262bd2613505d0c41644db0c7c65429fb1071f29c51235
Timestamp: 1736046360 Timestamp [UCT]: 2025-01-05 03:06:00 Age [y:d:h:m:s]: 00:164:04:22:09
Block: 1190454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117045 RingCT/type: yes/0
Extra: 0159c9d5f1891e8df7a9262bd2613505d0c41644db0c7c65429fb1071f29c51235021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 351f4a96e5fa9bbd32b744d7effc6af750848d56ff09c9409d3f70f3c917ab59 0.600000000000 1676971 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": 1190464, "vin": [ { "gen": { "height": 1190454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "351f4a96e5fa9bbd32b744d7effc6af750848d56ff09c9409d3f70f3c917ab59" } } ], "extra": [ 1, 89, 201, 213, 241, 137, 30, 141, 247, 169, 38, 43, 210, 97, 53, 5, 208, 196, 22, 68, 219, 12, 124, 101, 66, 159, 177, 7, 31, 41, 197, 18, 53, 2, 17, 0, 0, 0, 4, 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