Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f60541860f77f35cba19f3e8cb019179b0902aed4dcf28b30ebea3a3271231a

Tx prefix hash: b94fc41d86a1dcfa48e05f690e844f49141d92fa4e42a24fa6faa6c4bee92f1f
Tx public key: 933da767edda8f90a0d591f7e0f9860f4adefcf64be667b61ea57496329fef1a
Timestamp: 1736975190 Timestamp [UCT]: 2025-01-15 21:06:30 Age [y:d:h:m:s]: 00:309:09:35:56
Block: 1198135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218634 RingCT/type: yes/0
Extra: 01933da767edda8f90a0d591f7e0f9860f4adefcf64be667b61ea57496329fef1a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97363d81f5a972d661c6e2644e0602bdbe91c94002c0fb4b8fce26b985838190 0.600000000000 1684754 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": 1198145, "vin": [ { "gen": { "height": 1198135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97363d81f5a972d661c6e2644e0602bdbe91c94002c0fb4b8fce26b985838190" } } ], "extra": [ 1, 147, 61, 167, 103, 237, 218, 143, 144, 160, 213, 145, 247, 224, 249, 134, 15, 74, 222, 252, 246, 75, 230, 103, 182, 30, 165, 116, 150, 50, 159, 239, 26, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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