Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec11ccdfe1394d97de1b233d66d2afe8b7de20336b75957cb20cc85cf8b9e3e1

Tx prefix hash: 6945a295c814ddf4941a3e2bfcb58c4deb7350693fe4bd24829544e1ee80e417
Tx public key: 5bb52596a8b8b2bb78a60f3cfdedde39d5fb9e3fc0462bb576ed622183d95fca
Timestamp: 1710332664 Timestamp [UCT]: 2024-03-13 12:24:24 Age [y:d:h:m:s]: 01:005:23:15:13
Block: 977428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265248 RingCT/type: yes/0
Extra: 015bb52596a8b8b2bb78a60f3cfdedde39d5fb9e3fc0462bb576ed622183d95fca0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4022f4894095346a05f0ed27624ef89634c1c02442efd6897b8ff65ae794eef7 0.600000000000 1437431 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": 977438, "vin": [ { "gen": { "height": 977428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4022f4894095346a05f0ed27624ef89634c1c02442efd6897b8ff65ae794eef7" } } ], "extra": [ 1, 91, 181, 37, 150, 168, 184, 178, 187, 120, 166, 15, 60, 253, 237, 222, 57, 213, 251, 158, 63, 192, 70, 43, 181, 118, 237, 98, 33, 131, 217, 95, 202, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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