Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fbb631072507814ab7acd52eaaa1b877afbba599c1bf381737ee51a911c9924

Tx prefix hash: dc413736c471e3bdd1041df8e18944565dfa8fed1c3c9a2582818c9cf8165084
Tx public key: 4bffc4cf4859dae2fcc42bb7faabefef1a5e192a7901df84e3e41e264e8b6dfb
Timestamp: 1736339096 Timestamp [UCT]: 2025-01-08 12:24:56 Age [y:d:h:m:s]: 00:118:14:20:40
Block: 1192879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84559 RingCT/type: yes/0
Extra: 014bffc4cf4859dae2fcc42bb7faabefef1a5e192a7901df84e3e41e264e8b6dfb02110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43419f0f470882eca6555e1cb5900d8b089a9883ddf93f20688b917fb4593c48 0.600000000000 1679436 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": 1192889, "vin": [ { "gen": { "height": 1192879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43419f0f470882eca6555e1cb5900d8b089a9883ddf93f20688b917fb4593c48" } } ], "extra": [ 1, 75, 255, 196, 207, 72, 89, 218, 226, 252, 196, 43, 183, 250, 171, 239, 239, 26, 94, 25, 42, 121, 1, 223, 132, 227, 228, 30, 38, 78, 139, 109, 251, 2, 17, 0, 0, 0, 13, 31, 10, 83, 235, 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