Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ff45159441518ad5fdfff856b4988f4fe34012ec0cb8f6f52420ee81b409913

Tx prefix hash: 6074cb5b5074cb688d1adcba32ecd2c58e7d491e446a4b82a470385ec74021e0
Tx public key: 7940262c71f623f8308df24c1c9d10e04c3bf4c1724843ab763bd458f8e1bc79
Timestamp: 1706343116 Timestamp [UCT]: 2024-01-27 08:11:56 Age [y:d:h:m:s]: 01:082:01:59:16
Block: 944308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319766 RingCT/type: yes/0
Extra: 017940262c71f623f8308df24c1c9d10e04c3bf4c1724843ab763bd458f8e1bc790211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30221dc41266ade278c4ee2238ebc661bd978adef45d7d2423a316f560cadbd1 0.600000000000 1402544 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": 944318, "vin": [ { "gen": { "height": 944308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30221dc41266ade278c4ee2238ebc661bd978adef45d7d2423a316f560cadbd1" } } ], "extra": [ 1, 121, 64, 38, 44, 113, 246, 35, 248, 48, 141, 242, 76, 28, 157, 16, 224, 76, 59, 244, 193, 114, 72, 67, 171, 118, 59, 212, 88, 248, 225, 188, 121, 2, 17, 0, 0, 0, 2, 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