Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe9dd18c75e64b0707a90a39daf260e20936f2b8fb244f6846408f974e3ebba1

Tx prefix hash: 3c4b508bcc92a33d3faf49d37837d23f82cebb4f400aa8be8d3579657d8a6e6a
Tx public key: a102dcbc17ad0e75396835917ea1da33c50371503a078ec56889a31ea49edfc3
Timestamp: 1645586021 Timestamp [UCT]: 2022-02-23 03:13:41 Age [y:d:h:m:s]: 03:065:12:47:44
Block: 444487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 826921 RingCT/type: yes/0
Extra: 01a102dcbc17ad0e75396835917ea1da33c50371503a078ec56889a31ea49edfc302110000000ebf7ee4e7000000000000000000

1 output(s) for total of 20.666708799000 dcy

stealth address amount amount idx
00: 4fae83384628b4aa95bdcae2002c0bab5853ad11bca711e2f54d0052ea00fbc7 20.666708799000 857784 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": 444497, "vin": [ { "gen": { "height": 444487 } } ], "vout": [ { "amount": 20666708799, "target": { "key": "4fae83384628b4aa95bdcae2002c0bab5853ad11bca711e2f54d0052ea00fbc7" } } ], "extra": [ 1, 161, 2, 220, 188, 23, 173, 14, 117, 57, 104, 53, 145, 126, 161, 218, 51, 197, 3, 113, 80, 58, 7, 142, 197, 104, 137, 163, 30, 164, 158, 223, 195, 2, 17, 0, 0, 0, 14, 191, 126, 228, 231, 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