Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 944e6c155407b7d8f92361db0054407cb171ecdace006952428bd6af4f5ab60d

Tx prefix hash: 20b8a9a3f1e0ae96ffd95e6e65d8bbcce7a026a3cb9f93e853bfba8c79c5cb9a
Tx public key: 3331054c2fa8847410ffdbfdc72cf8b5a42f734cd27f722010fe2dabd6f3e234
Timestamp: 1728823302 Timestamp [UCT]: 2024-10-13 12:41:42 Age [y:d:h:m:s]: 00:102:19:35:17
Block: 1130708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73450 RingCT/type: yes/0
Extra: 013331054c2fa8847410ffdbfdc72cf8b5a42f734cd27f722010fe2dabd6f3e23402110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bb9b842afe77c8d7512e97d6ef774aa9a5547b4c0aad3627369045bf0357f3d 0.600000000000 1613585 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": 1130718, "vin": [ { "gen": { "height": 1130708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bb9b842afe77c8d7512e97d6ef774aa9a5547b4c0aad3627369045bf0357f3d" } } ], "extra": [ 1, 51, 49, 5, 76, 47, 168, 132, 116, 16, 255, 219, 253, 199, 44, 248, 181, 164, 47, 115, 76, 210, 127, 114, 32, 16, 254, 45, 171, 214, 243, 226, 52, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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