Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49d89394efe2b533d443bd927ce450727e37f7c8f958ebcda64f38279187f34f

Tx prefix hash: 2559f59c761084b241c7ee99c6673ac5a49383d6fa98195dede35ef9bdd0010e
Tx public key: d4789a5392f3336cc4e8f8a00111d660eeb3a64e39caef19a00d7dbdd71c3dca
Timestamp: 1609219914 Timestamp [UCT]: 2020-12-29 05:31:54 Age [y:d:h:m:s]: 03:363:02:18:59
Block: 171218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1012234 RingCT/type: yes/0
Extra: 01d4789a5392f3336cc4e8f8a00111d660eeb3a64e39caef19a00d7dbdd71c3dca02110000098290ce5c0f000000000000000000

1 output(s) for total of 166.220411845000 dcy

stealth address amount amount idx
00: 770a845ad63b8f53ab93e770cfe2ab5d90f591a7cf23d52c94bec36edc6e37fb 166.220411845000 322055 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": 171228, "vin": [ { "gen": { "height": 171218 } } ], "vout": [ { "amount": 166220411845, "target": { "key": "770a845ad63b8f53ab93e770cfe2ab5d90f591a7cf23d52c94bec36edc6e37fb" } } ], "extra": [ 1, 212, 120, 154, 83, 146, 243, 51, 108, 196, 232, 248, 160, 1, 17, 214, 96, 238, 179, 166, 78, 57, 202, 239, 25, 160, 13, 125, 189, 215, 28, 61, 202, 2, 17, 0, 0, 9, 130, 144, 206, 92, 15, 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