Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60168dd5ff027909b345d89428da7633b1caf50e234ce4fc8cbcdb3cb858a4f8

Tx prefix hash: dd0a9705b3b492387460b160add512bcabed74ba2ac6b90869830395b7e9656f
Tx public key: 85e47d011f6f74a6c51bd45bfbd7c82e90bbe132af8eea4d5147e0e82885c87b
Timestamp: 1711678249 Timestamp [UCT]: 2024-03-29 02:10:49 Age [y:d:h:m:s]: 00:300:01:19:25
Block: 988584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214715 RingCT/type: yes/0
Extra: 0185e47d011f6f74a6c51bd45bfbd7c82e90bbe132af8eea4d5147e0e82885c87b02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5a79e047f1356172bf5fb0d253c4b1f6b7000689f6a3cb9ea2285f8d0c8a56a 0.600000000000 1448863 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": 988594, "vin": [ { "gen": { "height": 988584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5a79e047f1356172bf5fb0d253c4b1f6b7000689f6a3cb9ea2285f8d0c8a56a" } } ], "extra": [ 1, 133, 228, 125, 1, 31, 111, 116, 166, 197, 27, 212, 91, 251, 215, 200, 46, 144, 187, 225, 50, 175, 142, 234, 77, 81, 71, 224, 232, 40, 133, 200, 123, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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