Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f871ce5e8f623519eb01ebb588eec31930d2fa09af8b741175b1b31bcd3d66c

Tx prefix hash: 05fc679eff37170d3074b27431a80c1efbda6ced26b144e4c7a2f7baa2bb968a
Tx public key: 2444ac6adfd378b381c1b36dd9f8b5f9557f516a4375e1fef04afdda1424250e
Timestamp: 1729005205 Timestamp [UCT]: 2024-10-15 15:13:25 Age [y:d:h:m:s]: 00:043:19:10:04
Block: 1132220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31269 RingCT/type: yes/0
Extra: 012444ac6adfd378b381c1b36dd9f8b5f9557f516a4375e1fef04afdda1424250e021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 458cab597a39c6d4a71ae669f9f81644cff5f071f239a9789fc6fdb8d2d86715 0.600000000000 1615133 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": 1132230, "vin": [ { "gen": { "height": 1132220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "458cab597a39c6d4a71ae669f9f81644cff5f071f239a9789fc6fdb8d2d86715" } } ], "extra": [ 1, 36, 68, 172, 106, 223, 211, 120, 179, 129, 193, 179, 109, 217, 248, 181, 249, 85, 127, 81, 106, 67, 117, 225, 254, 240, 74, 253, 218, 20, 36, 37, 14, 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