Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95a6e80657696698f5548b2e577722108a0f5c3b44fb8c9f9f3dedce0a271cf8

Tx prefix hash: d1c88c2931be157edf162673104225ec48bf3601da73dfa96efb1bc34786fc92
Tx public key: b369af9f653c9ecfcad0bc5d4a7b8e9355a46b38f148e5cf870459af0e823d68
Timestamp: 1581371965 Timestamp [UCT]: 2020-02-10 21:59:25 Age [y:d:h:m:s]: 05:107:23:51:00
Block: 62379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1229940 RingCT/type: yes/0
Extra: 01b369af9f653c9ecfcad0bc5d4a7b8e9355a46b38f148e5cf870459af0e823d680211000000034943cd9f000000000000000000

1 output(s) for total of 381.397137358000 dcy

stealth address amount amount idx
00: 8f8d739cb95ab8da76966f539c40348d7f6f88d3a43f8d753d4b7dec0ddc6ea8 381.397137358000 115059 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": 62389, "vin": [ { "gen": { "height": 62379 } } ], "vout": [ { "amount": 381397137358, "target": { "key": "8f8d739cb95ab8da76966f539c40348d7f6f88d3a43f8d753d4b7dec0ddc6ea8" } } ], "extra": [ 1, 179, 105, 175, 159, 101, 60, 158, 207, 202, 208, 188, 93, 74, 123, 142, 147, 85, 164, 107, 56, 241, 72, 229, 207, 135, 4, 89, 175, 14, 130, 61, 104, 2, 17, 0, 0, 0, 3, 73, 67, 205, 159, 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