Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b96fe6df6b7b8b6a7f508a6c13fb2ea7999e593c265edad023a07d3786a4a494

Tx prefix hash: 3485359e8089aef97ad276e19b1cefa2c0a6776e41da70ed099f8326f7a812c4
Tx public key: 7eaf84fed3ec4b2e725be0e07f31d82c1d6bedd536506f64a8aff42aaeb9e4ea
Timestamp: 1726515485 Timestamp [UCT]: 2024-09-16 19:38:05 Age [y:d:h:m:s]: 00:205:17:05:06
Block: 1111574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146848 RingCT/type: yes/0
Extra: 017eaf84fed3ec4b2e725be0e07f31d82c1d6bedd536506f64a8aff42aaeb9e4ea02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b9f9efdf8835f6b2797a8a8448cd7c36d7d7a033b13f4b92d005a3ac5493961 0.600000000000 1590583 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": 1111584, "vin": [ { "gen": { "height": 1111574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b9f9efdf8835f6b2797a8a8448cd7c36d7d7a033b13f4b92d005a3ac5493961" } } ], "extra": [ 1, 126, 175, 132, 254, 211, 236, 75, 46, 114, 91, 224, 224, 127, 49, 216, 44, 29, 107, 237, 213, 54, 80, 111, 100, 168, 175, 244, 42, 174, 185, 228, 234, 2, 17, 0, 0, 0, 9, 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