Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d6bd9424e4a8b1c16f84d8ddcc96d4576ddbfd64c238e056ee9f95cd85198fa

Tx prefix hash: d6c5dbe0ab08e42265b9a2b49e29bcd143e69d10d8baeaf981cc3f0dfdaae59e
Tx public key: f07df80574b512f4a8363a1b6b5a3d70bd2cf6a31c48c76e3f7a335591eb7a3f
Timestamp: 1728666541 Timestamp [UCT]: 2024-10-11 17:09:01 Age [y:d:h:m:s]: 00:104:05:20:58
Block: 1129406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74454 RingCT/type: yes/0
Extra: 01f07df80574b512f4a8363a1b6b5a3d70bd2cf6a31c48c76e3f7a335591eb7a3f021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03b5bbe265aaf09d3d9b493192e1e90d365157adbf375a3011a77a201d93c80e 0.600000000000 1612231 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": 1129416, "vin": [ { "gen": { "height": 1129406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03b5bbe265aaf09d3d9b493192e1e90d365157adbf375a3011a77a201d93c80e" } } ], "extra": [ 1, 240, 125, 248, 5, 116, 181, 18, 244, 168, 54, 58, 27, 107, 90, 61, 112, 189, 44, 246, 163, 28, 72, 199, 110, 63, 122, 51, 85, 145, 235, 122, 63, 2, 17, 0, 0, 0, 4, 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