Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24a22facc5f8386eb3269d055bfe96410645bcd94a34d11f6d8b457bbbc31e1e

Tx prefix hash: 66e6eb16c6e692c6a53a03bd905d0fbbd53266494d8e6f1a04a070220556cc3a
Tx public key: fd4d619228257ccda57e501949c9ab89a8a9856cee9ca85b1a284cd64da40bbd
Timestamp: 1729564840 Timestamp [UCT]: 2024-10-22 02:40:40 Age [y:d:h:m:s]: 00:092:02:33:43
Block: 1136812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65822 RingCT/type: yes/0
Extra: 01fd4d619228257ccda57e501949c9ab89a8a9856cee9ca85b1a284cd64da40bbd0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc86ecc51899172bd5f19d6404eadf766e80d3991e80874e5afe9922a294fbca 0.600000000000 1620189 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": 1136822, "vin": [ { "gen": { "height": 1136812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc86ecc51899172bd5f19d6404eadf766e80d3991e80874e5afe9922a294fbca" } } ], "extra": [ 1, 253, 77, 97, 146, 40, 37, 124, 205, 165, 126, 80, 25, 73, 201, 171, 137, 168, 169, 133, 108, 238, 156, 168, 91, 26, 40, 76, 214, 77, 164, 11, 189, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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