Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3abcdd6986e9c4c9611b1e1fb1e378f5c6f4a58c67548fd94b42d3f8b8107b59

Tx prefix hash: f1e29207eb84a3f29f8c17fecd946d8c4c377b8025dc4073962a4026a74837e6
Tx public key: 21f66d511040c4e55a0f930ac941c99695865f53d22fe99fd90a6a25409a46fb
Timestamp: 1724425158 Timestamp [UCT]: 2024-08-23 14:59:18 Age [y:d:h:m:s]: 00:225:06:23:33
Block: 1094255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160844 RingCT/type: yes/0
Extra: 0121f66d511040c4e55a0f930ac941c99695865f53d22fe99fd90a6a25409a46fb021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dee2efa7150676b3c58a4ca0964a7093c6a9e27ba04472b1461f76b6e5f0e06d 0.600000000000 1569364 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": 1094265, "vin": [ { "gen": { "height": 1094255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dee2efa7150676b3c58a4ca0964a7093c6a9e27ba04472b1461f76b6e5f0e06d" } } ], "extra": [ 1, 33, 246, 109, 81, 16, 64, 196, 229, 90, 15, 147, 10, 201, 65, 201, 150, 149, 134, 95, 83, 210, 47, 233, 159, 217, 10, 106, 37, 64, 154, 70, 251, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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