Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcaf01762eecb445847ba6f224aafa303e891478dd9d628dab1119c5bddc02c0

Tx prefix hash: 125371a09b2d143813f25be28afb32b717df91cefa8a62c0b3c77838b5cada46
Tx public key: d0531542e2e907cff0b02fa90cfe68586b1fdb1e715ce8c1deba283abe8ab531
Timestamp: 1724070024 Timestamp [UCT]: 2024-08-19 12:20:24 Age [y:d:h:m:s]: 00:252:02:47:32
Block: 1091302 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180074 RingCT/type: yes/0
Extra: 01d0531542e2e907cff0b02fa90cfe68586b1fdb1e715ce8c1deba283abe8ab53102110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6860ea141b83f95a8ef964d9b3071925cc0b6c9765990f30eae0b2e8d18b316 0.600000000000 1565933 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": 1091312, "vin": [ { "gen": { "height": 1091302 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6860ea141b83f95a8ef964d9b3071925cc0b6c9765990f30eae0b2e8d18b316" } } ], "extra": [ 1, 208, 83, 21, 66, 226, 233, 7, 207, 240, 176, 47, 169, 12, 254, 104, 88, 107, 31, 219, 30, 113, 92, 232, 193, 222, 186, 40, 58, 190, 138, 181, 49, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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