Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abcd587cd1ebaa552a410268cfe16b33989a70483d6818e540639561a97daf0e

Tx prefix hash: 77bf461ed4ae42201aa068ef3970b5cac888a77a48f26914f19c1b84edce6c30
Tx public key: f6cc9b26e7b1d6e01d9442a4bd35ada3af16337e63db8a4dbc28d177611a7aa2
Timestamp: 1726465894 Timestamp [UCT]: 2024-09-16 05:51:34 Age [y:d:h:m:s]: 00:205:16:48:30
Block: 1111156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146845 RingCT/type: yes/0
Extra: 01f6cc9b26e7b1d6e01d9442a4bd35ada3af16337e63db8a4dbc28d177611a7aa202110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef2a786b4501387b4c446efbcd39c11dc28fef226bcec765a84beca7f7d0cb9d 0.600000000000 1590019 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": 1111166, "vin": [ { "gen": { "height": 1111156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef2a786b4501387b4c446efbcd39c11dc28fef226bcec765a84beca7f7d0cb9d" } } ], "extra": [ 1, 246, 204, 155, 38, 231, 177, 214, 224, 29, 148, 66, 164, 189, 53, 173, 163, 175, 22, 51, 126, 99, 219, 138, 77, 188, 40, 209, 119, 97, 26, 122, 162, 2, 17, 0, 0, 0, 3, 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