Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d8c2bcec7bc40c5a0726f1efbb896e16b33eabe81feaa87a44115a03ad0b8a1

Tx prefix hash: 898d964f5b952af91b6d0db93107a44872ea71e682fe82818608317416cbd7c5
Tx public key: 48c7d5c7b1b5fbde87bac58e1ca3221bc1bbd0a2d84934583778b1f6e616836f
Timestamp: 1716315781 Timestamp [UCT]: 2024-05-21 18:23:01 Age [y:d:h:m:s]: 00:235:16:38:34
Block: 1027013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168683 RingCT/type: yes/0
Extra: 0148c7d5c7b1b5fbde87bac58e1ca3221bc1bbd0a2d84934583778b1f6e616836f0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dab5fc54fb5915676154374bcdc9f9231d34b1cf5fbb66c89d56ee31ece912e9 0.600000000000 1494412 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": 1027023, "vin": [ { "gen": { "height": 1027013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dab5fc54fb5915676154374bcdc9f9231d34b1cf5fbb66c89d56ee31ece912e9" } } ], "extra": [ 1, 72, 199, 213, 199, 177, 181, 251, 222, 135, 186, 197, 142, 28, 163, 34, 27, 193, 187, 208, 162, 216, 73, 52, 88, 55, 120, 177, 246, 230, 22, 131, 111, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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