Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc00534074fe30b668fb718c5056c37e51394654de0148f0c1b8a6bd0ba4eae7

Tx prefix hash: 26fcb0f251e4df0c609ccce37c2f0c1058bb5987cc0bc7c91b2e3af4909e1878
Tx public key: 93d54a56f3e29c25ae643b48fd0a97734bcc981ccdbae167b240bff83d0789cd
Timestamp: 1725020885 Timestamp [UCT]: 2024-08-30 12:28:05 Age [y:d:h:m:s]: 00:222:18:24:02
Block: 1099177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159075 RingCT/type: yes/0
Extra: 0193d54a56f3e29c25ae643b48fd0a97734bcc981ccdbae167b240bff83d0789cd02110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf8e57acdfde714f89e136e7cc56b4fb65abf2c7691deb2560077ff1474e00e0 0.600000000000 1575106 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": 1099187, "vin": [ { "gen": { "height": 1099177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf8e57acdfde714f89e136e7cc56b4fb65abf2c7691deb2560077ff1474e00e0" } } ], "extra": [ 1, 147, 213, 74, 86, 243, 226, 156, 37, 174, 100, 59, 72, 253, 10, 151, 115, 75, 204, 152, 28, 205, 186, 225, 103, 178, 64, 191, 248, 61, 7, 137, 205, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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