Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b0cb0a121bbd15dc2cce3eff1364a6d64a7d75e947d8f988d6e322c11048b24

Tx prefix hash: b5a2ed48080b736423bde722a1bccb2365aee5520d6d1ee2ed32ad7f1b705cbd
Tx public key: eabd6d75b44e555d9a0c8d03c83643bf18e2c2d1ff11b36fbc1898348338428c
Timestamp: 1733196899 Timestamp [UCT]: 2024-12-03 03:34:59 Age [y:d:h:m:s]: 00:110:06:47:02
Block: 1166868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78626 RingCT/type: yes/0
Extra: 01eabd6d75b44e555d9a0c8d03c83643bf18e2c2d1ff11b36fbc1898348338428c021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37498e2471ef42e74320fff0d94d48847c7ce9d40c2475ec29057a41da515dc7 0.600000000000 1652559 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": 1166878, "vin": [ { "gen": { "height": 1166868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37498e2471ef42e74320fff0d94d48847c7ce9d40c2475ec29057a41da515dc7" } } ], "extra": [ 1, 234, 189, 109, 117, 180, 78, 85, 93, 154, 12, 141, 3, 200, 54, 67, 191, 24, 226, 194, 209, 255, 17, 179, 111, 188, 24, 152, 52, 131, 56, 66, 140, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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