Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acbd50002103f72f2c0ee9ac74f220359b0eac8be7bb14708206aa916e46dad0

Tx prefix hash: ae92c1fba9abf2278babff3524cbd725a04215b9047677b798e7d80df0da00ea
Tx public key: 87c1fa4a590a94f30c5feb643e046aa460cc0e13ba8fb84610cd33f76e85f0a4
Timestamp: 1726505470 Timestamp [UCT]: 2024-09-16 16:51:10 Age [y:d:h:m:s]: 01:052:06:30:22
Block: 1111488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295769 RingCT/type: yes/0
Extra: 0187c1fa4a590a94f30c5feb643e046aa460cc0e13ba8fb84610cd33f76e85f0a4021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64c0505342d8817fb5c1d07d86084cd66dd4c15bd96746827d1c14cae9843993 0.600000000000 1590467 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": 1111498, "vin": [ { "gen": { "height": 1111488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64c0505342d8817fb5c1d07d86084cd66dd4c15bd96746827d1c14cae9843993" } } ], "extra": [ 1, 135, 193, 250, 74, 89, 10, 148, 243, 12, 95, 235, 100, 62, 4, 106, 164, 96, 204, 14, 19, 186, 143, 184, 70, 16, 205, 51, 247, 110, 133, 240, 164, 2, 17, 0, 0, 0, 3, 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