Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 065c98801b13161e8b5684a6f13c8fd9d7371acb711caf681b35947c6619da33

Tx prefix hash: 7b5dc9a9e28eb306daac48e78e7d594dd2289ba9eac209b048f2f88965628b7e
Tx public key: 7ffc2f93cc5b564c90af4ab7ba7edcf11717e0259e56e51d8ff399c06a6ebf78
Timestamp: 1728484916 Timestamp [UCT]: 2024-10-09 14:41:56 Age [y:d:h:m:s]: 00:252:21:34:02
Block: 1127899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180436 RingCT/type: yes/0
Extra: 017ffc2f93cc5b564c90af4ab7ba7edcf11717e0259e56e51d8ff399c06a6ebf7802110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5599aaba5eed2e8d229d8f7012f954535fc403327eb642eb2a8553fa0f92f3a 0.600000000000 1610712 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": 1127909, "vin": [ { "gen": { "height": 1127899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5599aaba5eed2e8d229d8f7012f954535fc403327eb642eb2a8553fa0f92f3a" } } ], "extra": [ 1, 127, 252, 47, 147, 204, 91, 86, 76, 144, 175, 74, 183, 186, 126, 220, 241, 23, 23, 224, 37, 158, 86, 229, 29, 143, 243, 153, 192, 106, 110, 191, 120, 2, 17, 0, 0, 0, 1, 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