Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd078200283bd19dbcbf4d05f623d9a2af7ac5f200e8b6b5380473dba42710c8

Tx prefix hash: 1d26e526afa45f30d813393d095034255d62fb3aab1be453ee8d0dd8bf163c99
Tx public key: a6667525a5cbeeb7b1bb47c27ffd1da6f0216e8fd78b8f01f197d82f74a6e707
Timestamp: 1747361350 Timestamp [UCT]: 2025-05-16 02:09:10 Age [y:d:h:m:s]: 00:221:15:48:34
Block: 1283852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156178 RingCT/type: yes/0
Extra: 01a6667525a5cbeeb7b1bb47c27ffd1da6f0216e8fd78b8f01f197d82f74a6e707021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f0826e909883c673589784f1f361ad8f86d46482d7573c75c95b8e028303cf8 0.600000000000 1771271 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": 1283862, "vin": [ { "gen": { "height": 1283852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f0826e909883c673589784f1f361ad8f86d46482d7573c75c95b8e028303cf8" } } ], "extra": [ 1, 166, 102, 117, 37, 165, 203, 238, 183, 177, 187, 71, 194, 127, 253, 29, 166, 240, 33, 110, 143, 215, 139, 143, 1, 241, 151, 216, 47, 116, 166, 231, 7, 2, 17, 0, 0, 0, 4, 228, 220, 144, 9, 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