Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1073505271b03c3a06e57067ebaf0e4e3a4b6d0fbfe2d1cacb97eddc0b5a6db1

Tx prefix hash: e524faa8e152066c433e6edbf0d9e5cd8eb52dd7ad4e255eea1b0c22484c0f07
Tx public key: 639d4b2abe6a49abdacfdbb58dfc590447ee24e90f78e8f55d2c401859897957
Timestamp: 1662631910 Timestamp [UCT]: 2022-09-08 10:11:50 Age [y:d:h:m:s]: 02:193:01:27:07
Block: 583397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 659279 RingCT/type: yes/0
Extra: 01639d4b2abe6a49abdacfdbb58dfc590447ee24e90f78e8f55d2c40185989795702110000000175e3f0e9000000000000000000

1 output(s) for total of 7.160834603000 dcy

stealth address amount amount idx
00: 1c130fc9fe68d12e0f9a132eca8224c42960640e77f1338279f05067ae85bd1b 7.160834603000 1017221 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": 583407, "vin": [ { "gen": { "height": 583397 } } ], "vout": [ { "amount": 7160834603, "target": { "key": "1c130fc9fe68d12e0f9a132eca8224c42960640e77f1338279f05067ae85bd1b" } } ], "extra": [ 1, 99, 157, 75, 42, 190, 106, 73, 171, 218, 207, 219, 181, 141, 252, 89, 4, 71, 238, 36, 233, 15, 120, 232, 245, 93, 44, 64, 24, 89, 137, 121, 87, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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