Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1b80bcb9f327d6090b22c67310cb6eae5d43b590adfc73d41cb2fa18ed89c69

Tx prefix hash: c2e030a8eef2edb9ad55c1da2add278b6ed031c7e6c8ecff6800ad62e330ec38
Tx public key: 3ce854d0ebe253b3a31be30a92a320e6dec84ea4f00d702dd97b715c3410087c
Timestamp: 1723522385 Timestamp [UCT]: 2024-08-13 04:13:05 Age [y:d:h:m:s]: 00:237:13:12:40
Block: 1086758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169646 RingCT/type: yes/0
Extra: 013ce854d0ebe253b3a31be30a92a320e6dec84ea4f00d702dd97b715c3410087c021100000019e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de61f58975a831c88fdc374d3ad4e55ae989bef3478fb4fbd318128c25e5c13e 0.600000000000 1561357 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": 1086768, "vin": [ { "gen": { "height": 1086758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de61f58975a831c88fdc374d3ad4e55ae989bef3478fb4fbd318128c25e5c13e" } } ], "extra": [ 1, 60, 232, 84, 208, 235, 226, 83, 179, 163, 27, 227, 10, 146, 163, 32, 230, 222, 200, 78, 164, 240, 13, 112, 45, 217, 123, 113, 92, 52, 16, 8, 124, 2, 17, 0, 0, 0, 25, 233, 20, 221, 21, 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