Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a20522d89f9a33ed3902fc94b5417f93fb17e08a47c644e09c71471b215a1bd

Tx prefix hash: dd967d1bc9ca6692a368bb392d7dd529d5a31f798b143a808088a43b56616632
Tx public key: 36695bde0f1561d17fe50e11417c8c5d405c33da9aee450fe9e2acbde6375fa4
Timestamp: 1577852838 Timestamp [UCT]: 2020-01-01 04:27:18 Age [y:d:h:m:s]: 05:040:11:24:47
Block: 36139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1178748 RingCT/type: yes/0
Extra: 0136695bde0f1561d17fe50e11417c8c5d405c33da9aee450fe9e2acbde6375fa40211000000414ac5aa02000000000000000000

1 output(s) for total of 465.862061623000 dcy

stealth address amount amount idx
00: b9a7a9526abc1bd0df99e8416cc404534b3b1e66f18ece409127fa79b2246c03 465.862061623000 61123 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": 36149, "vin": [ { "gen": { "height": 36139 } } ], "vout": [ { "amount": 465862061623, "target": { "key": "b9a7a9526abc1bd0df99e8416cc404534b3b1e66f18ece409127fa79b2246c03" } } ], "extra": [ 1, 54, 105, 91, 222, 15, 21, 97, 209, 127, 229, 14, 17, 65, 124, 140, 93, 64, 92, 51, 218, 154, 238, 69, 15, 233, 226, 172, 189, 230, 55, 95, 164, 2, 17, 0, 0, 0, 65, 74, 197, 170, 2, 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