Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf5419b102fdd87afcdbf2af527b2def640ee75f3a02e00d930727c2111fa9ca

Tx prefix hash: 0f35d43710e3296c905fdb53b0b8d7a34ec2cd4e5de42a671b9e01bb299c7408
Tx public key: 8fb3eedd8c33f0b0d9670a4750d9d19427e14ca48876e88d6798e91c4db5dd95
Timestamp: 1752600216 Timestamp [UCT]: 2025-07-15 17:23:36 Age [y:d:h:m:s]: 00:133:21:41:49
Block: 1326154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94457 RingCT/type: yes/0
Extra: 018fb3eedd8c33f0b0d9670a4750d9d19427e14ca48876e88d6798e91c4db5dd95021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4891d6c3b5a000189364cb3ad9c228dab6034ea1989b18031a84a7e769180b8 0.600000000000 1813903 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": 1326164, "vin": [ { "gen": { "height": 1326154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4891d6c3b5a000189364cb3ad9c228dab6034ea1989b18031a84a7e769180b8" } } ], "extra": [ 1, 143, 179, 238, 221, 140, 51, 240, 176, 217, 103, 10, 71, 80, 217, 209, 148, 39, 225, 76, 164, 136, 118, 232, 141, 103, 152, 233, 28, 77, 181, 221, 149, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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