Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f485639c5adeb08a8c5a3c7eed2fcf8e5d0ad540705d7139efa58691a0dd4f1

Tx prefix hash: 0dafe39f3b4fd98d0f9708d8b6afa7f460cb1c1bc45cd1abbaf1ab8384f8e7d6
Tx public key: 8cb9b44f76eef314424e382864ba6dd224ab2e03922bc81f0227b2825fd08ae3
Timestamp: 1698373418 Timestamp [UCT]: 2023-10-27 02:23:38 Age [y:d:h:m:s]: 01:193:21:29:37
Block: 878476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399598 RingCT/type: yes/0
Extra: 018cb9b44f76eef314424e382864ba6dd224ab2e03922bc81f0227b2825fd08ae30211000000034b8f5122000000000000000000

1 output(s) for total of 0.753779556000 dcy

stealth address amount amount idx
00: 0e9994af217744d90bd2d64d4370c59dc022ad3afc8512c5362a45764562da14 0.753779556000 1333924 of 0

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": 878486, "vin": [ { "gen": { "height": 878476 } } ], "vout": [ { "amount": 753779556, "target": { "key": "0e9994af217744d90bd2d64d4370c59dc022ad3afc8512c5362a45764562da14" } } ], "extra": [ 1, 140, 185, 180, 79, 118, 238, 243, 20, 66, 78, 56, 40, 100, 186, 109, 210, 36, 171, 46, 3, 146, 43, 200, 31, 2, 39, 178, 130, 95, 208, 138, 227, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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