Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7521365ec6209f5a0865477e7c4c634dbceecfc03d6f2b580f1ec0302e2c427e

Tx prefix hash: 679169976f61aa560c2e0c0299481d46b3994aa8df42908c039adc644851c7c0
Tx public key: a985ad2147567bc06ab2ecebade77d5ba1dd6ce3501372a4b9a7f08c94fb8c2c
Timestamp: 1723456377 Timestamp [UCT]: 2024-08-12 09:52:57 Age [y:d:h:m:s]: 00:217:02:21:12
Block: 1086210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155055 RingCT/type: yes/0
Extra: 01a985ad2147567bc06ab2ecebade77d5ba1dd6ce3501372a4b9a7f08c94fb8c2c02110000001491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a036e04473f9f2a96dddb4c509801d4fc39204d8abc651c7294bea865eafd47 0.600000000000 1560805 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": 1086220, "vin": [ { "gen": { "height": 1086210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a036e04473f9f2a96dddb4c509801d4fc39204d8abc651c7294bea865eafd47" } } ], "extra": [ 1, 169, 133, 173, 33, 71, 86, 123, 192, 106, 178, 236, 235, 173, 231, 125, 91, 161, 221, 108, 227, 80, 19, 114, 164, 185, 167, 240, 140, 148, 251, 140, 44, 2, 17, 0, 0, 0, 20, 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