Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23640464ce502799593d8a3977729747b2bfb3368fec9a174b071114624e5cf4

Tx prefix hash: 9b201bd1ed0894066689a8d8015c694b37d567d1243bdeffdb98b48820929207
Tx public key: 2c752448bfdfd6f01f28fdab2f916c5b9d4e08c4fb1d4469da3c82ed238f68b4
Timestamp: 1710341049 Timestamp [UCT]: 2024-03-13 14:44:09 Age [y:d:h:m:s]: 00:303:03:51:42
Block: 977495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216998 RingCT/type: yes/0
Extra: 012c752448bfdfd6f01f28fdab2f916c5b9d4e08c4fb1d4469da3c82ed238f68b40211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 277c0901a17a3015ab56cc97029a0d8b169e13a9182764b8148c50a859b09f28 0.600000000000 1437498 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": 977505, "vin": [ { "gen": { "height": 977495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "277c0901a17a3015ab56cc97029a0d8b169e13a9182764b8148c50a859b09f28" } } ], "extra": [ 1, 44, 117, 36, 72, 191, 223, 214, 240, 31, 40, 253, 171, 47, 145, 108, 91, 157, 78, 8, 196, 251, 29, 68, 105, 218, 60, 130, 237, 35, 143, 104, 180, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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