Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd2598b89accc2150df286d252774e31356b520e6cdde66abce434e8d1766611

Tx prefix hash: 99c9dacab5cbb66c3bb0db71137df8d324e40be4c0d9265361e623bb32c60295
Tx public key: 8aeb07f573bb1f4056d843c4d4e89523905a0574000aa4cbe81975671ac74b32
Timestamp: 1709850633 Timestamp [UCT]: 2024-03-07 22:30:33 Age [y:d:h:m:s]: 01:070:22:50:05
Block: 973422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311721 RingCT/type: yes/0
Extra: 018aeb07f573bb1f4056d843c4d4e89523905a0574000aa4cbe81975671ac74b320211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a9d946b9e107888f3b362d3d4c626db616194e426e4110b8aa93748af47c2db 0.600000000000 1433357 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": 973432, "vin": [ { "gen": { "height": 973422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a9d946b9e107888f3b362d3d4c626db616194e426e4110b8aa93748af47c2db" } } ], "extra": [ 1, 138, 235, 7, 245, 115, 187, 31, 64, 86, 216, 67, 196, 212, 232, 149, 35, 144, 90, 5, 116, 0, 10, 164, 203, 232, 25, 117, 103, 26, 199, 75, 50, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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