Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd791d6c081fafd1bb550afc2c900d21ed45d8d6c5fe5778556585536b5b2ec5

Tx prefix hash: fe32e66266ca0dc8e67dbf0f666e461fa8a845bd1bb9b923d3bdd6a6fe6f62b4
Tx public key: c10c33bbb8b148f526f65a1880aa6c9cda1073cebc890cae628712f09d409e1b
Timestamp: 1576928195 Timestamp [UCT]: 2019-12-21 11:36:35 Age [y:d:h:m:s]: 05:009:18:32:33
Block: 29263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1156266 RingCT/type: yes/0
Extra: 01c10c33bbb8b148f526f65a1880aa6c9cda1073cebc890cae628712f09d409e1b0211000000149159db1e000000000000000000

1 output(s) for total of 490.953540993000 dcy

stealth address amount amount idx
00: 2f13e22c5599cdd39441f161ef0143cb16d57fba01be96d6a5ee7c0ee3e3ad8d 490.953540993000 48091 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": 29273, "vin": [ { "gen": { "height": 29263 } } ], "vout": [ { "amount": 490953540993, "target": { "key": "2f13e22c5599cdd39441f161ef0143cb16d57fba01be96d6a5ee7c0ee3e3ad8d" } } ], "extra": [ 1, 193, 12, 51, 187, 184, 177, 72, 245, 38, 246, 90, 24, 128, 170, 108, 156, 218, 16, 115, 206, 188, 137, 12, 174, 98, 135, 18, 240, 157, 64, 158, 27, 2, 17, 0, 0, 0, 20, 145, 89, 219, 30, 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