Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3de19ffc84c5c0f9fb36301a6369423d0e2c06353aaa826eb08c581cfb38f4d

Tx prefix hash: ab9e5ff32eac5b785428e48d7016eebdc8d2d47a75c698eed6d063197742058c
Tx public key: e1af70d17f189650b3f3b12a8ce2c703edf8935ba7753691e43d75af0f5cbfd7
Timestamp: 1670400108 Timestamp [UCT]: 2022-12-07 08:01:48 Age [y:d:h:m:s]: 02:130:03:56:54
Block: 647229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 614746 RingCT/type: yes/0
Extra: 01e1af70d17f189650b3f3b12a8ce2c703edf8935ba7753691e43d75af0f5cbfd702110000000583600029000000000000000000

1 output(s) for total of 4.400090774000 dcy

stealth address amount amount idx
00: 922d123fab99c7cf2de6763e7790aeb9214f1d79afa0ed96d2f2be12c08e4c4d 4.400090774000 1087494 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": 647239, "vin": [ { "gen": { "height": 647229 } } ], "vout": [ { "amount": 4400090774, "target": { "key": "922d123fab99c7cf2de6763e7790aeb9214f1d79afa0ed96d2f2be12c08e4c4d" } } ], "extra": [ 1, 225, 175, 112, 209, 127, 24, 150, 80, 179, 243, 177, 42, 140, 226, 199, 3, 237, 248, 147, 91, 167, 117, 54, 145, 228, 61, 117, 175, 15, 92, 191, 215, 2, 17, 0, 0, 0, 5, 131, 96, 0, 41, 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