Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4417095324a665582b4d742a347af195d65b824d462117bfe8ba41d60d600f4

Tx prefix hash: 13db34d6fb545dcefbe0759a24ffdcf1dda40b9704c3493cd7c2a80a0a793fd4
Tx public key: 2db4c2985e66de088cc601e512b0ab89ea56f809aea5fca845d0f7431226c57a
Timestamp: 1709071481 Timestamp [UCT]: 2024-02-27 22:04:41 Age [y:d:h:m:s]: 01:084:22:29:21
Block: 966961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321746 RingCT/type: yes/0
Extra: 012db4c2985e66de088cc601e512b0ab89ea56f809aea5fca845d0f7431226c57a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc5c0f9f1e7b6f4338c4f16be55d628525d9a36e4a9909ec4cb3ba963aefbcb9 0.600000000000 1426732 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": 966971, "vin": [ { "gen": { "height": 966961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc5c0f9f1e7b6f4338c4f16be55d628525d9a36e4a9909ec4cb3ba963aefbcb9" } } ], "extra": [ 1, 45, 180, 194, 152, 94, 102, 222, 8, 140, 198, 1, 229, 18, 176, 171, 137, 234, 86, 248, 9, 174, 165, 252, 168, 69, 208, 247, 67, 18, 38, 197, 122, 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