Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 587ae5eb04902d045beff3e2f7d8fe282a011c8dc151fceb45a5eb00f6e57f47

Tx prefix hash: fb4a7e94e5d36112392014995ac78cf8b35f473cadcde7075f8e95a6d9476c53
Tx public key: 5a1f5de1d0dcaeefb95eccbab4f8fa3ad47683738cadbacb32afcc11adc75fca
Timestamp: 1633184444 Timestamp [UCT]: 2021-10-02 14:20:44 Age [y:d:h:m:s]: 03:054:20:58:38
Block: 345230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 816133 RingCT/type: yes/0
Extra: 015a1f5de1d0dcaeefb95eccbab4f8fa3ad47683738cadbacb32afcc11adc75fca02110000000637cb3088000000000000000000

1 output(s) for total of 44.067419040000 dcy

stealth address amount amount idx
00: 5260a07019071b682081e704f9bacabec1c3e8b379dce73f7b0e59262f06c676 44.067419040000 708196 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": 345240, "vin": [ { "gen": { "height": 345230 } } ], "vout": [ { "amount": 44067419040, "target": { "key": "5260a07019071b682081e704f9bacabec1c3e8b379dce73f7b0e59262f06c676" } } ], "extra": [ 1, 90, 31, 93, 225, 208, 220, 174, 239, 185, 94, 204, 186, 180, 248, 250, 58, 212, 118, 131, 115, 140, 173, 186, 203, 50, 175, 204, 17, 173, 199, 95, 202, 2, 17, 0, 0, 0, 6, 55, 203, 48, 136, 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