Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec774a6b51712c27bb04c8ec2b6f8f5fde6ad1f24c8dbf8b2a985ea050120b5f

Tx prefix hash: bd408fc0bb1b5622a43be2bd001a43b38abbb8af54b819b692387a5dbdc42821
Tx public key: c223a96a68857932150d80da57d751ddcf980a06f7d6b5b98080068c92c33a98
Timestamp: 1720257678 Timestamp [UCT]: 2024-07-06 09:21:18 Age [y:d:h:m:s]: 00:313:01:37:56
Block: 1059687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223727 RingCT/type: yes/0
Extra: 01c223a96a68857932150d80da57d751ddcf980a06f7d6b5b98080068c92c33a9802110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8093310c92d3eda3e252fefc81e0207a1a424290f03f45a4bbbdb236e9ff21a8 0.600000000000 1530158 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": 1059697, "vin": [ { "gen": { "height": 1059687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8093310c92d3eda3e252fefc81e0207a1a424290f03f45a4bbbdb236e9ff21a8" } } ], "extra": [ 1, 194, 35, 169, 106, 104, 133, 121, 50, 21, 13, 128, 218, 87, 215, 81, 221, 207, 152, 10, 6, 247, 214, 181, 185, 128, 128, 6, 140, 146, 195, 58, 152, 2, 17, 0, 0, 0, 13, 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