Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcfd96026aa91d459d2661b32fce57aa105b5214f4fd91d7f087639ac2cd833c

Tx prefix hash: 578141271203f9d4f6aafb15a6a0308d40a14f85987b1c231f48c7b21cda312b
Tx public key: 7af303d7fb43391915de3089bd6c53f5c65a5cad89418495636ce9dec6231d61
Timestamp: 1710835592 Timestamp [UCT]: 2024-03-19 08:06:32 Age [y:d:h:m:s]: 01:083:13:38:41
Block: 981601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320729 RingCT/type: yes/0
Extra: 017af303d7fb43391915de3089bd6c53f5c65a5cad89418495636ce9dec6231d6102110000001352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f69dc9cfec6158d563ed7366f6fa031b879994b5f507e835b1e20348f229eae8 0.600000000000 1441698 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": 981611, "vin": [ { "gen": { "height": 981601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f69dc9cfec6158d563ed7366f6fa031b879994b5f507e835b1e20348f229eae8" } } ], "extra": [ 1, 122, 243, 3, 215, 251, 67, 57, 25, 21, 222, 48, 137, 189, 108, 83, 245, 198, 90, 92, 173, 137, 65, 132, 149, 99, 108, 233, 222, 198, 35, 29, 97, 2, 17, 0, 0, 0, 19, 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