Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a10a83c2cead3bf703613fe75d53e1061ec172934a27260ac8fe082680f21d7

Tx prefix hash: f24b9816c8b9dc2d5ff86e2607f88b515204e7ef38cf2e6fc8ede6b8e73c3710
Tx public key: 1d3354dc4ab75220a4c4b0a33c5719a1bb0a5b8c567d075dbf9022b63761d8d9
Timestamp: 1583346367 Timestamp [UCT]: 2020-03-04 18:26:07 Age [y:d:h:m:s]: 04:296:21:06:14
Block: 76369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106591 RingCT/type: yes/0
Extra: 011d3354dc4ab75220a4c4b0a33c5719a1bb0a5b8c567d075dbf9022b63761d8d902110000003b026b59f3000000000000000000

1 output(s) for total of 342.735109904000 dcy

stealth address amount amount idx
00: edb8feabbc86fd075280c973efab4a90265e0a7d683aba3f354cc84902a0fa44 342.735109904000 140616 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": 76379, "vin": [ { "gen": { "height": 76369 } } ], "vout": [ { "amount": 342735109904, "target": { "key": "edb8feabbc86fd075280c973efab4a90265e0a7d683aba3f354cc84902a0fa44" } } ], "extra": [ 1, 29, 51, 84, 220, 74, 183, 82, 32, 164, 196, 176, 163, 60, 87, 25, 161, 187, 10, 91, 140, 86, 125, 7, 93, 191, 144, 34, 182, 55, 97, 216, 217, 2, 17, 0, 0, 0, 59, 2, 107, 89, 243, 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