Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec74723045ee4bafeb4cefbf6d4409827a53be49f2c98fefdfb97decf9493e7a

Tx prefix hash: 15f511222f47d90c4894a98ad43ee51c0422791e1c5fe8122fe897c6afdf9f0d
Tx public key: f90c91df8bfdfeeefbd3f6bfc29584bad0e494ced9e6d44223eb92c44ca4e3de
Timestamp: 1721853314 Timestamp [UCT]: 2024-07-24 20:35:14 Age [y:d:h:m:s]: 00:321:04:47:37
Block: 1072914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229523 RingCT/type: yes/0
Extra: 01f90c91df8bfdfeeefbd3f6bfc29584bad0e494ced9e6d44223eb92c44ca4e3de021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0b93cf5e511ca0f0864e59562d4a7e2a82de36349ed192893007c0d05e779f6 0.600000000000 1545411 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": 1072924, "vin": [ { "gen": { "height": 1072914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0b93cf5e511ca0f0864e59562d4a7e2a82de36349ed192893007c0d05e779f6" } } ], "extra": [ 1, 249, 12, 145, 223, 139, 253, 254, 238, 251, 211, 246, 191, 194, 149, 132, 186, 208, 228, 148, 206, 217, 230, 212, 66, 35, 235, 146, 196, 76, 164, 227, 222, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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