Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b6cd1f8c4f4c1a79da95789d9a0aa0eb713bbbf46a3c23a28038236e477578b

Tx prefix hash: 0d7da2073c9fdf77abab276ba022654cf167566bbb6a8e9018947031f6eb309a
Tx public key: 855ed80b75dcf0bcaebc360bf86d6562f357132f57e894ecb52946473c802564
Timestamp: 1625571110 Timestamp [UCT]: 2021-07-06 11:31:50 Age [y:d:h:m:s]: 03:176:20:01:16
Block: 289141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 896426 RingCT/type: yes/0
Extra: 01855ed80b75dcf0bcaebc360bf86d6562f357132f57e894ecb52946473c802564021100000029694a138f000000000000000000

1 output(s) for total of 67.601501979000 dcy

stealth address amount amount idx
00: 270d89f3b5fff6e59320c3885f85d3af6d380be5b58e2defa951ce5b6c67ccd8 67.601501979000 605634 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": 289151, "vin": [ { "gen": { "height": 289141 } } ], "vout": [ { "amount": 67601501979, "target": { "key": "270d89f3b5fff6e59320c3885f85d3af6d380be5b58e2defa951ce5b6c67ccd8" } } ], "extra": [ 1, 133, 94, 216, 11, 117, 220, 240, 188, 174, 188, 54, 11, 248, 109, 101, 98, 243, 87, 19, 47, 87, 232, 148, 236, 181, 41, 70, 71, 60, 128, 37, 100, 2, 17, 0, 0, 0, 41, 105, 74, 19, 143, 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