Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5b7163232608cb3e019256e22e9b34416ff13cc2ef967046ee2ce888b4abf2d

Tx prefix hash: 009a4b60d97414e732ac77ef7ace98f1d42b04bd43ff6be10ae29db1a822fae6
Tx public key: b79cb618bdd0c8231a0ccbe633041460e83c9206f46ec7e4cb9ae41569e2e4b1
Timestamp: 1696767017 Timestamp [UCT]: 2023-10-08 12:10:17 Age [y:d:h:m:s]: 01:184:20:22:27
Block: 865150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393147 RingCT/type: yes/0
Extra: 01b79cb618bdd0c8231a0ccbe633041460e83c9206f46ec7e4cb9ae41569e2e4b1021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.834447357000 dcy

stealth address amount amount idx
00: 33905d0a44b252b5ed23c395a1df0dc2cd0776a7a30c8c4789dfc212fc3e7859 0.834447357000 1319676 of 0

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": 865160, "vin": [ { "gen": { "height": 865150 } } ], "vout": [ { "amount": 834447357, "target": { "key": "33905d0a44b252b5ed23c395a1df0dc2cd0776a7a30c8c4789dfc212fc3e7859" } } ], "extra": [ 1, 183, 156, 182, 24, 189, 208, 200, 35, 26, 12, 203, 230, 51, 4, 20, 96, 232, 60, 146, 6, 244, 110, 199, 228, 203, 154, 228, 21, 105, 226, 228, 177, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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