Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52f2a542de580a27a64dc76b81f4e9cd624b2466d1d2661e1b8c74ab0d598ea9

Tx prefix hash: f7bdb4ca4f65ac16a3fd69da9a1f59d0a60f38970ed7ccbef79f57a3ee72227c
Tx public key: 3a2115defe2297c37afcb68dd0fd758e063b136a661ca7a5a994e40c21fead19
Timestamp: 1657276102 Timestamp [UCT]: 2022-07-08 10:28:22 Age [y:d:h:m:s]: 03:116:07:08:15
Block: 539255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 862827 RingCT/type: yes/0
Extra: 013a2115defe2297c37afcb68dd0fd758e063b136a661ca7a5a994e40c21fead190211000000014da16a3a000000000000000000

1 output(s) for total of 10.028234423000 dcy

stealth address amount amount idx
00: 481cbe9e70f8251037c7dd863cc9f030b8cdb74cceec47c6c311e5670ecd184d 10.028234423000 969336 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": 539265, "vin": [ { "gen": { "height": 539255 } } ], "vout": [ { "amount": 10028234423, "target": { "key": "481cbe9e70f8251037c7dd863cc9f030b8cdb74cceec47c6c311e5670ecd184d" } } ], "extra": [ 1, 58, 33, 21, 222, 254, 34, 151, 195, 122, 252, 182, 141, 208, 253, 117, 142, 6, 59, 19, 106, 102, 28, 167, 165, 169, 148, 228, 12, 33, 254, 173, 25, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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