Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d332c949f63d40cc2b1349747ffc9115fce3b0b44a8b1782f3468d81da07b3cf

Tx prefix hash: eeef189497a5d0a18c494543a12a8ef1476a9d8c14c4acbf7b89ff7d045d4e27
Tx public key: 9e1faef4ca1286eaead98ea89901a41353bd1a509a93d9b830e05cab20a16864
Timestamp: 1728527689 Timestamp [UCT]: 2024-10-10 02:34:49 Age [y:d:h:m:s]: 00:170:04:14:14
Block: 1128256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121406 RingCT/type: yes/0
Extra: 019e1faef4ca1286eaead98ea89901a41353bd1a509a93d9b830e05cab20a1686402110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 428a8ccd93e06eb12bad8e22d552a4fb757530fd3e623370684f416c2071663f 0.600000000000 1611073 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": 1128266, "vin": [ { "gen": { "height": 1128256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "428a8ccd93e06eb12bad8e22d552a4fb757530fd3e623370684f416c2071663f" } } ], "extra": [ 1, 158, 31, 174, 244, 202, 18, 134, 234, 234, 217, 142, 168, 153, 1, 164, 19, 83, 189, 26, 80, 154, 147, 217, 184, 48, 224, 92, 171, 32, 161, 104, 100, 2, 17, 0, 0, 0, 1, 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