Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a51785879c012b5066a88f5eec3308f73fd9348d12a3e8d0e00e4ff36fe55d1a

Tx prefix hash: b98358c83be1c773525451be76a1f04900788791ec325c726b419588636f1236
Tx public key: b04ea64bf455f5c0b3cb6a912751824ee5011f0fd9cbf9012daabea0d543ff98
Timestamp: 1719982615 Timestamp [UCT]: 2024-07-03 04:56:55 Age [y:d:h:m:s]: 00:306:16:54:48
Block: 1057405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219164 RingCT/type: yes/0
Extra: 01b04ea64bf455f5c0b3cb6a912751824ee5011f0fd9cbf9012daabea0d543ff980211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7335a863a029a0b3d6404b5531a6869b17e1aefeb5bb603ac787c5633bfff30d 0.600000000000 1527840 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": 1057415, "vin": [ { "gen": { "height": 1057405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7335a863a029a0b3d6404b5531a6869b17e1aefeb5bb603ac787c5633bfff30d" } } ], "extra": [ 1, 176, 78, 166, 75, 244, 85, 245, 192, 179, 203, 106, 145, 39, 81, 130, 78, 229, 1, 31, 15, 217, 203, 249, 1, 45, 170, 190, 160, 213, 67, 255, 152, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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