Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 779a15c7e6ff54a374c04e7c730c3bf6332280e5b3c43b45e8410ab0b8b7ad52

Tx prefix hash: 63c9f6db37736f6d4d98f09e649ae3dc2c041da243c607b1ff7c59b054402269
Tx public key: 20c4a1d19c034d55942b7f305ea162c9cbe89379bdb2d3b8c6e2a302ec079026
Timestamp: 1702869472 Timestamp [UCT]: 2023-12-18 03:17:52 Age [y:d:h:m:s]: 01:338:01:54:23
Block: 915534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500493 RingCT/type: yes/0
Extra: 0120c4a1d19c034d55942b7f305ea162c9cbe89379bdb2d3b8c6e2a302ec07902602110000001175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb51cdc3619278b12efb54da02a85ea30792080b6eb6fb39948623579d24251f 0.600000000000 1372930 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": 915544, "vin": [ { "gen": { "height": 915534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb51cdc3619278b12efb54da02a85ea30792080b6eb6fb39948623579d24251f" } } ], "extra": [ 1, 32, 196, 161, 209, 156, 3, 77, 85, 148, 43, 127, 48, 94, 161, 98, 201, 203, 232, 147, 121, 189, 178, 211, 184, 198, 226, 163, 2, 236, 7, 144, 38, 2, 17, 0, 0, 0, 17, 117, 227, 240, 233, 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