Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83696260cd420adb66174ecb5dbbea30be7349f8c570ac8dd14942983f4ccce3

Tx prefix hash: e499f5bc80ca6529162ecbbf77a0896e204bc1d3182cbe4cf484381751c25b85
Tx public key: 17f5b75f4665d5c3a32f1c6c7c5f871d193737e9ef2bded36f2ee00aa98e3339
Timestamp: 1729520822 Timestamp [UCT]: 2024-10-21 14:27:02 Age [y:d:h:m:s]: 00:143:16:18:12
Block: 1136443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102506 RingCT/type: yes/0
Extra: 0117f5b75f4665d5c3a32f1c6c7c5f871d193737e9ef2bded36f2ee00aa98e3339021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: caf206d09d2ff74ca7a9d49d04db3c45db5b6894b35790903bd931eb21e26a41 0.600000000000 1619788 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": 1136453, "vin": [ { "gen": { "height": 1136443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "caf206d09d2ff74ca7a9d49d04db3c45db5b6894b35790903bd931eb21e26a41" } } ], "extra": [ 1, 23, 245, 183, 95, 70, 101, 213, 195, 163, 47, 28, 108, 124, 95, 135, 29, 25, 55, 55, 233, 239, 43, 222, 211, 111, 46, 224, 10, 169, 142, 51, 57, 2, 17, 0, 0, 0, 1, 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