Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc1e42becbbeb2e70252010c57c70102d6180e0ccd07ca2a8d7a07fe389e61c0

Tx prefix hash: 72ba8d88eb84059751f04f7c5ce5d5d834ff53f8d1c1465ccbb2cc04ac76c9d6
Tx public key: 8557c4d8d4d20e23bf3bfcd3b16a8cea4e4d87e94eaec73a3a60e69b4d9a4436
Timestamp: 1623052697 Timestamp [UCT]: 2021-06-07 07:58:17 Age [y:d:h:m:s]: 03:341:10:23:42
Block: 273758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1008448 RingCT/type: yes/0
Extra: 018557c4d8d4d20e23bf3bfcd3b16a8cea4e4d87e94eaec73a3a60e69b4d9a443602110000000723fdb90b000000000000000000

1 output(s) for total of 76.019784157000 dcy

stealth address amount amount idx
00: 1ecc348c5aaff129512f27a8cf66823c96d581c271972335c5307a4a45cd3b62 76.019784157000 574355 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": 273768, "vin": [ { "gen": { "height": 273758 } } ], "vout": [ { "amount": 76019784157, "target": { "key": "1ecc348c5aaff129512f27a8cf66823c96d581c271972335c5307a4a45cd3b62" } } ], "extra": [ 1, 133, 87, 196, 216, 212, 210, 14, 35, 191, 59, 252, 211, 177, 106, 140, 234, 78, 77, 135, 233, 78, 174, 199, 58, 58, 96, 230, 155, 77, 154, 68, 54, 2, 17, 0, 0, 0, 7, 35, 253, 185, 11, 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