Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41ce5c4ed2739b413cd3b7b52369d5ac8400591d4196b0141f9035aaa0caddee

Tx prefix hash: b6562513567ae55440b0d99a8e3f8305bddc8db9a63be0ff1b69d0a8a8e1e410
Tx public key: d49951f992a6d26e9278e393a8df47030faf9869707be0e13c33d0d86d43c172
Timestamp: 1736749352 Timestamp [UCT]: 2025-01-13 06:22:32 Age [y:d:h:m:s]: 00:156:07:48:28
Block: 1196276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111420 RingCT/type: yes/0
Extra: 01d49951f992a6d26e9278e393a8df47030faf9869707be0e13c33d0d86d43c172021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ea2d71360dcd904bd35ea9e31da76150040e045da17288c70b35f48fb5b9462 0.600000000000 1682873 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": 1196286, "vin": [ { "gen": { "height": 1196276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ea2d71360dcd904bd35ea9e31da76150040e045da17288c70b35f48fb5b9462" } } ], "extra": [ 1, 212, 153, 81, 249, 146, 166, 210, 110, 146, 120, 227, 147, 168, 223, 71, 3, 15, 175, 152, 105, 112, 123, 224, 225, 60, 51, 208, 216, 109, 67, 193, 114, 2, 17, 0, 0, 0, 1, 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