Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b0522cab2d4aa37ce90bc2313f9d84b4a59d2270010d8d0e3a0c638a044d5a6

Tx prefix hash: 60b5e140a2efe9d4b36b6cb2adf1bc24b6664c34cb76beec81a9ad609fdcb0ed
Tx public key: a94c5e8c9b5547d11072e8991de1e4d6998114ee2ea5e1d2611ece4f01fadeea
Timestamp: 1735946648 Timestamp [UCT]: 2025-01-03 23:24:08 Age [y:d:h:m:s]: 00:166:19:10:03
Block: 1189632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118906 RingCT/type: yes/0
Extra: 01a94c5e8c9b5547d11072e8991de1e4d6998114ee2ea5e1d2611ece4f01fadeea02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a172e069f35e13189c7441ebf3f36ed4823c520b6a71ad3f087d0f1693ebfdb3 0.600000000000 1676143 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": 1189642, "vin": [ { "gen": { "height": 1189632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a172e069f35e13189c7441ebf3f36ed4823c520b6a71ad3f087d0f1693ebfdb3" } } ], "extra": [ 1, 169, 76, 94, 140, 155, 85, 71, 209, 16, 114, 232, 153, 29, 225, 228, 214, 153, 129, 20, 238, 46, 165, 225, 210, 97, 30, 206, 79, 1, 250, 222, 234, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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