Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee2c091fe4f37c4b15362855826e8080711df63e46f4faeaebbfd8725789bb7a

Tx prefix hash: 18e1bf31dd85a4049f203aaed5d45f3eb7a14c92db9c0f0a9690613170a0ef78
Tx public key: 4f6b2f596da87766dc67f826c78ad0b74bc96736615c58d85245d323d0e07011
Timestamp: 1718949023 Timestamp [UCT]: 2024-06-21 05:50:23 Age [y:d:h:m:s]: 00:281:04:32:26
Block: 1048854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200915 RingCT/type: yes/0
Extra: 014f6b2f596da87766dc67f826c78ad0b74bc96736615c58d85245d323d0e070110211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce82989a11d8f0fd35172dd960969a9afbd642a1f2cee0db606d0f8a8bcc68af 0.600000000000 1518941 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": 1048864, "vin": [ { "gen": { "height": 1048854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce82989a11d8f0fd35172dd960969a9afbd642a1f2cee0db606d0f8a8bcc68af" } } ], "extra": [ 1, 79, 107, 47, 89, 109, 168, 119, 102, 220, 103, 248, 38, 199, 138, 208, 183, 75, 201, 103, 54, 97, 92, 88, 216, 82, 69, 211, 35, 208, 224, 112, 17, 2, 17, 0, 0, 0, 1, 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