Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 367e26201ffb778b3d51af52f5c1ea90ce5e472bfe343f285eaf81d56b57ab3b

Tx prefix hash: 2195510a1a5cabe652a5656a6044ee040c87610c030b415fd5a5ad33d5cb4c51
Tx public key: 7673978b3f8f85c99bdefab8eba84c98db58d02f406b07a0e6887e5270a87a49
Timestamp: 1582098450 Timestamp [UCT]: 2020-02-19 07:47:30 Age [y:d:h:m:s]: 05:084:06:10:02
Block: 67927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1213428 RingCT/type: yes/0
Extra: 017673978b3f8f85c99bdefab8eba84c98db58d02f406b07a0e6887e5270a87a490211000000094943cd9f000000000000000000

1 output(s) for total of 365.536254829000 dcy

stealth address amount amount idx
00: f87716a1dda394df7b6d63239bc87f9f3b699fed5705783bfbfffd2302b69c0f 365.536254829000 125147 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": 67937, "vin": [ { "gen": { "height": 67927 } } ], "vout": [ { "amount": 365536254829, "target": { "key": "f87716a1dda394df7b6d63239bc87f9f3b699fed5705783bfbfffd2302b69c0f" } } ], "extra": [ 1, 118, 115, 151, 139, 63, 143, 133, 201, 155, 222, 250, 184, 235, 168, 76, 152, 219, 88, 208, 47, 64, 107, 7, 160, 230, 136, 126, 82, 112, 168, 122, 73, 2, 17, 0, 0, 0, 9, 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