Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f3ef09e37b6452dc99cb17d5ee93c11e4ee12c198e48be65336f290b4d01d63

Tx prefix hash: 02051fdbae6b9261ca2ae4ab69cdefdbe58ec4b50402838eccd952fe0d20ed44
Tx public key: 6a4c9b4f5e5c89d4d98e8e6654c603b7b27494daedd33b39771cf3e9086df57e
Timestamp: 1629554311 Timestamp [UCT]: 2021-08-21 13:58:31 Age [y:d:h:m:s]: 03:263:09:01:25
Block: 318237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 961946 RingCT/type: yes/0
Extra: 016a4c9b4f5e5c89d4d98e8e6654c603b7b27494daedd33b39771cf3e9086df57e02110000001737cb3088000000000000000000

1 output(s) for total of 54.143855293000 dcy

stealth address amount amount idx
00: 9f83490d728a19da6b4f9cce39b02ae7f0290fe61105252a8f4ac5bb75f0f619 54.143855293000 661494 of 0

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": 318247, "vin": [ { "gen": { "height": 318237 } } ], "vout": [ { "amount": 54143855293, "target": { "key": "9f83490d728a19da6b4f9cce39b02ae7f0290fe61105252a8f4ac5bb75f0f619" } } ], "extra": [ 1, 106, 76, 155, 79, 94, 92, 137, 212, 217, 142, 142, 102, 84, 198, 3, 183, 178, 116, 148, 218, 237, 211, 59, 57, 119, 28, 243, 233, 8, 109, 245, 126, 2, 17, 0, 0, 0, 23, 55, 203, 48, 136, 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