Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec177930e2603fafe355a0f2286c81d7d591544d51edde89cde78a02af2252c9

Tx prefix hash: 65293e439c86ecb5b8b2554091ae41d64487153106dc720ba4f3edab6bba9eb2
Tx public key: e9e97842bf13f4f089b1ce55b7c3ef9084a6825b7de763aa22826f9f33c60905
Timestamp: 1617421084 Timestamp [UCT]: 2021-04-03 03:38:04 Age [y:d:h:m:s]: 03:269:08:40:22
Block: 232178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 952102 RingCT/type: yes/0
Extra: 01e9e97842bf13f4f089b1ce55b7c3ef9084a6825b7de763aa22826f9f33c6090502110000001e0dc70aa7000000000000000000

1 output(s) for total of 104.401325392000 dcy

stealth address amount amount idx
00: 50aab49fa6451d7896238ba1b7bcfedc2f767bd5f15e5874f10f955bc98307f2 104.401325392000 482408 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": 232188, "vin": [ { "gen": { "height": 232178 } } ], "vout": [ { "amount": 104401325392, "target": { "key": "50aab49fa6451d7896238ba1b7bcfedc2f767bd5f15e5874f10f955bc98307f2" } } ], "extra": [ 1, 233, 233, 120, 66, 191, 19, 244, 240, 137, 177, 206, 85, 183, 195, 239, 144, 132, 166, 130, 91, 125, 231, 99, 170, 34, 130, 111, 159, 51, 198, 9, 5, 2, 17, 0, 0, 0, 30, 13, 199, 10, 167, 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