Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da5b977fa19fd82bcaa7e85750021f6813841ab93cd6ea6f2ccb945441c3b946

Tx prefix hash: 71adad2abf0c25283e9c80b25a752799d10292068cac8a5d32fc7acd0610678b
Tx public key: fe6b8386f8bb196f7b236a32a5094af0adb239be916c1f31bf97e6d687ba6efb
Timestamp: 1736254589 Timestamp [UCT]: 2025-01-07 12:56:29 Age [y:d:h:m:s]: 00:348:14:12:33
Block: 1192175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246695 RingCT/type: yes/0
Extra: 01fe6b8386f8bb196f7b236a32a5094af0adb239be916c1f31bf97e6d687ba6efb021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17edc9be403c4b5798749a831226d5a4733cc4078fc70af29110ec9ebef90d40 0.600000000000 1678724 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": 1192185, "vin": [ { "gen": { "height": 1192175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17edc9be403c4b5798749a831226d5a4733cc4078fc70af29110ec9ebef90d40" } } ], "extra": [ 1, 254, 107, 131, 134, 248, 187, 25, 111, 123, 35, 106, 50, 165, 9, 74, 240, 173, 178, 57, 190, 145, 108, 31, 49, 191, 151, 230, 214, 135, 186, 110, 251, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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