Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45796cf029cf805b25734ac836556cd53ae10dc54c3137a0701f608bc350ef62

Tx prefix hash: 34e23f2e05c2a916c13d41585e17bd606a413e700304f6088dc5847a71a7d85c
Tx public key: 27924601495a2ec1107e262b5a29c60b5ff65f2484565ef80dfbe8d800693f0a
Timestamp: 1631249176 Timestamp [UCT]: 2021-09-10 04:46:16 Age [y:d:h:m:s]: 03:111:11:31:22
Block: 330882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 854950 RingCT/type: yes/0
Extra: 0127924601495a2ec1107e262b5a29c60b5ff65f2484565ef80dfbe8d800693f0a02110000000aa272b9cb000000000000000000

1 output(s) for total of 49.164431717000 dcy

stealth address amount amount idx
00: df74ecf87f0a5c45c32a3d3cc54b5d8bf907409a28b5d25441b774f086eb3164 49.164431717000 683939 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": 330892, "vin": [ { "gen": { "height": 330882 } } ], "vout": [ { "amount": 49164431717, "target": { "key": "df74ecf87f0a5c45c32a3d3cc54b5d8bf907409a28b5d25441b774f086eb3164" } } ], "extra": [ 1, 39, 146, 70, 1, 73, 90, 46, 193, 16, 126, 38, 43, 90, 41, 198, 11, 95, 246, 95, 36, 132, 86, 94, 248, 13, 251, 232, 216, 0, 105, 63, 10, 2, 17, 0, 0, 0, 10, 162, 114, 185, 203, 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