Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da861d6e7c37a0c3d620f2aabf4d48f6f4f14820d4e44110dcc296234bde8426

Tx prefix hash: 325af601b06d9ca6f195b55307d2c51f9e28fc68c372eada58f540dbb2958f70
Tx public key: efddb5e722565f392274edccd6e497891b85f5f0d707509bc2b68505561be586
Timestamp: 1728054291 Timestamp [UCT]: 2024-10-04 15:04:51 Age [y:d:h:m:s]: 00:190:10:27:24
Block: 1124342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135884 RingCT/type: yes/0
Extra: 01efddb5e722565f392274edccd6e497891b85f5f0d707509bc2b68505561be586021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71ef7c1d1e47c16a7a0ae6ca2a3aab0ea0d9c5795c3e2b6052a8ded473a1d530 0.600000000000 1606959 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": 1124352, "vin": [ { "gen": { "height": 1124342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71ef7c1d1e47c16a7a0ae6ca2a3aab0ea0d9c5795c3e2b6052a8ded473a1d530" } } ], "extra": [ 1, 239, 221, 181, 231, 34, 86, 95, 57, 34, 116, 237, 204, 214, 228, 151, 137, 27, 133, 245, 240, 215, 7, 80, 155, 194, 182, 133, 5, 86, 27, 229, 134, 2, 17, 0, 0, 0, 1, 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