Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6971ec6e0c2e5114c26463f39757a07ef2b2ea5e7f4e12ee7fadfc8ec480bbe

Tx prefix hash: cd3bcf79dced0f6630f978bdd7b4afd4eaf3c2afda4d9a388472e95b6fc16591
Tx public key: e8cc0d692fa8828016f2d0035f2786e820ac07873ed8f85acfeba05b1e625aab
Timestamp: 1728539298 Timestamp [UCT]: 2024-10-10 05:48:18 Age [y:d:h:m:s]: 00:155:13:19:48
Block: 1128350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110972 RingCT/type: yes/0
Extra: 01e8cc0d692fa8828016f2d0035f2786e820ac07873ed8f85acfeba05b1e625aab02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2acfeb0daf1987dfe8afcf044d80177968e40582cf00d2e5b1cdf6be934dcae9 0.600000000000 1611167 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": 1128360, "vin": [ { "gen": { "height": 1128350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2acfeb0daf1987dfe8afcf044d80177968e40582cf00d2e5b1cdf6be934dcae9" } } ], "extra": [ 1, 232, 204, 13, 105, 47, 168, 130, 128, 22, 242, 208, 3, 95, 39, 134, 232, 32, 172, 7, 135, 62, 216, 248, 90, 207, 235, 160, 91, 30, 98, 90, 171, 2, 17, 0, 0, 0, 4, 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