Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e113ffcf5e2ea95af80ee351c8d2be6deb530527f3090e1647845a70c2746d05

Tx prefix hash: 0d0e2e887451c0f8f48f92d204c10fcb348a9d0f9df67961fbd56a49b755e83b
Tx public key: f867378808b2050ab8e109cd5dbe0c0b4cc251cb3c3986b8eb149905c9f4ed2a
Timestamp: 1713846032 Timestamp [UCT]: 2024-04-23 04:20:32 Age [y:d:h:m:s]: 00:342:15:31:44
Block: 1006536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244945 RingCT/type: yes/0
Extra: 01f867378808b2050ab8e109cd5dbe0c0b4cc251cb3c3986b8eb149905c9f4ed2a02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42caaace2faab37133c51f2840d141e6f7ae2af2c78e42d7de41a42857c986ea 0.600000000000 1467594 of 15

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": 1006546, "vin": [ { "gen": { "height": 1006536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42caaace2faab37133c51f2840d141e6f7ae2af2c78e42d7de41a42857c986ea" } } ], "extra": [ 1, 248, 103, 55, 136, 8, 178, 5, 10, 184, 225, 9, 205, 93, 190, 12, 11, 76, 194, 81, 203, 60, 57, 134, 184, 235, 20, 153, 5, 201, 244, 237, 42, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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