Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36d99a5847132909317e97385fdb1c238028ea8189e5f79378fc837c28c1e5a5

Tx prefix hash: cc96310d3425ccd4c2e57a5e2d17ec24171d66ad7789717976c181f1d70863dc
Tx public key: 79a013ec57dc790be0e8b8e018c9095116dd60dd4367d5bc479e0b3988f46cdf
Timestamp: 1727385129 Timestamp [UCT]: 2024-09-26 21:12:09 Age [y:d:h:m:s]: 00:117:21:59:38
Block: 1118778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84271 RingCT/type: yes/0
Extra: 0179a013ec57dc790be0e8b8e018c9095116dd60dd4367d5bc479e0b3988f46cdf021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9c29ae8a0f9c5cde4c51819b8c25f5b01c83d021211e255a30b3f73cf9aeedc 0.600000000000 1600091 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": 1118788, "vin": [ { "gen": { "height": 1118778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9c29ae8a0f9c5cde4c51819b8c25f5b01c83d021211e255a30b3f73cf9aeedc" } } ], "extra": [ 1, 121, 160, 19, 236, 87, 220, 121, 11, 224, 232, 184, 224, 24, 201, 9, 81, 22, 221, 96, 221, 67, 103, 213, 188, 71, 158, 11, 57, 136, 244, 108, 223, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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