Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57f064adb28447a621d94934676707e6c8673e805fe3fb010ef6efa0a9be1b3f

Tx prefix hash: 44dadf728f7bf777c599563955eba46e96682b32200f5803e3f38ae77f450d4e
Tx public key: 80ff95ed1c706aa07d8cb9a2a0bed0e8f110f8735fe2ef7d87e7859165114ac2
Timestamp: 1717139700 Timestamp [UCT]: 2024-05-31 07:15:00 Age [y:d:h:m:s]: 00:305:17:01:54
Block: 1033846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218473 RingCT/type: yes/0
Extra: 0180ff95ed1c706aa07d8cb9a2a0bed0e8f110f8735fe2ef7d87e7859165114ac20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bd547494aacc493977c9a0a6b68e37afbb1686c4c83a63d0c45911d3ecf5796 0.600000000000 1502319 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": 1033856, "vin": [ { "gen": { "height": 1033846 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bd547494aacc493977c9a0a6b68e37afbb1686c4c83a63d0c45911d3ecf5796" } } ], "extra": [ 1, 128, 255, 149, 237, 28, 112, 106, 160, 125, 140, 185, 162, 160, 190, 208, 232, 241, 16, 248, 115, 95, 226, 239, 125, 135, 231, 133, 145, 101, 17, 74, 194, 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