Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78d255e9c8d16e86575ef31de73c3d207c6945e9ad4ec89e70b47a0db1a88f25

Tx prefix hash: b9cc557ab058d21bd99832d863ce06657c2dc62f8e06afe8584e148e0213606f
Tx public key: 83c165f3cb1cc06596dfa6f0cb8f9a37924911566df40b61bba94506519478b5
Timestamp: 1702592618 Timestamp [UCT]: 2023-12-14 22:23:38 Age [y:d:h:m:s]: 01:028:21:29:42
Block: 913232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282000 RingCT/type: yes/0
Extra: 0183c165f3cb1cc06596dfa6f0cb8f9a37924911566df40b61bba94506519478b5021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 662ea9b03cfbbf42a466a2e2a82be17ddb75254ccb08d2fc676e403bdc4c403d 0.600000000000 1370486 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": 913242, "vin": [ { "gen": { "height": 913232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "662ea9b03cfbbf42a466a2e2a82be17ddb75254ccb08d2fc676e403bdc4c403d" } } ], "extra": [ 1, 131, 193, 101, 243, 203, 28, 192, 101, 150, 223, 166, 240, 203, 143, 154, 55, 146, 73, 17, 86, 109, 244, 11, 97, 187, 169, 69, 6, 81, 148, 120, 181, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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