Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c90c7c14ac4e4a5a70d43a78c38947b41eb9347d339563fff2d6f8b6754d6b92

Tx prefix hash: f0b0e1d8ce3b78810b7e9a29642f9605216f60c4f6f14cbcfd5c3db441045c6f
Tx public key: 3532b9f087e507e1a833c0dad61c4d4b40462b96812cc2349927006a50e4443a
Timestamp: 1694059406 Timestamp [UCT]: 2023-09-07 04:03:26 Age [y:d:h:m:s]: 01:129:14:11:46
Block: 842676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353957 RingCT/type: yes/0
Extra: 013532b9f087e507e1a833c0dad61c4d4b40462b96812cc2349927006a50e4443a0211000000134b8f5122000000000000000000

1 output(s) for total of 0.990523236000 dcy

stealth address amount amount idx
00: 58fbfa9666f40be69ba90575c32706ed4115daa8f8fc091e6c889e481587f485 0.990523236000 1295818 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": 842686, "vin": [ { "gen": { "height": 842676 } } ], "vout": [ { "amount": 990523236, "target": { "key": "58fbfa9666f40be69ba90575c32706ed4115daa8f8fc091e6c889e481587f485" } } ], "extra": [ 1, 53, 50, 185, 240, 135, 229, 7, 225, 168, 51, 192, 218, 214, 28, 77, 75, 64, 70, 43, 150, 129, 44, 194, 52, 153, 39, 0, 106, 80, 228, 68, 58, 2, 17, 0, 0, 0, 19, 75, 143, 81, 34, 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