Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd5fee7eb2e3935d8f52619d9d0087af63cae80db26c7b94fe7f7779b655994c

Tx prefix hash: 7f5bf5d2fc01ab69219cc5a6584f23b26934fe66ecb2a359642f882a426886a9
Tx public key: 14c50cc3712873a1e70f78aecba8714f6d211cfd3e4986b3e97b2bf040f96a75
Timestamp: 1734653758 Timestamp [UCT]: 2024-12-20 00:15:58 Age [y:d:h:m:s]: 00:106:06:54:07
Block: 1178954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75729 RingCT/type: yes/0
Extra: 0114c50cc3712873a1e70f78aecba8714f6d211cfd3e4986b3e97b2bf040f96a75021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecf15ac863050c770254399d91cfdcd32deb415bce2b2a5737e0b3e94f97a496 0.600000000000 1665345 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": 1178964, "vin": [ { "gen": { "height": 1178954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecf15ac863050c770254399d91cfdcd32deb415bce2b2a5737e0b3e94f97a496" } } ], "extra": [ 1, 20, 197, 12, 195, 113, 40, 115, 161, 231, 15, 120, 174, 203, 168, 113, 79, 109, 33, 28, 253, 62, 73, 134, 179, 233, 123, 43, 240, 64, 249, 106, 117, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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