Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fc07ad294fb3983f8751ae2ac14a706deacfd68cd33d182ec56e8747f74f34a

Tx prefix hash: eb10c56cc9416d9a14eebd2898e63fedef62edff8f4640b40226e42d8e8ae7f2
Tx public key: 0d075fa5272e8fc24d96fd507aeff07dcf61ad4e4cea80b0628bb680980d621c
Timestamp: 1704714781 Timestamp [UCT]: 2024-01-08 11:53:01 Age [y:d:h:m:s]: 01:127:11:08:21
Block: 930817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352242 RingCT/type: yes/0
Extra: 010d075fa5272e8fc24d96fd507aeff07dcf61ad4e4cea80b0628bb680980d621c02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34098e407b744b4c09d6c5f8d7743007b438d08c1df7485fde2420cb9d7e8d14 0.600000000000 1388707 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": 930827, "vin": [ { "gen": { "height": 930817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34098e407b744b4c09d6c5f8d7743007b438d08c1df7485fde2420cb9d7e8d14" } } ], "extra": [ 1, 13, 7, 95, 165, 39, 46, 143, 194, 77, 150, 253, 80, 122, 239, 240, 125, 207, 97, 173, 78, 76, 234, 128, 176, 98, 139, 182, 128, 152, 13, 98, 28, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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