Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e6b684e80e0ea5a0e49c41650344c4d13c921020f1d6e084957adbbf9475e42

Tx prefix hash: d0576a4c3b6f65619f6400eb14796ace18b9f91e0a144c5d9215bc5354e6fdc4
Tx public key: 0f6b3661069ae87274cef0b47887e1bb35b02194f07262ec88786d49a4bc5a36
Timestamp: 1578956473 Timestamp [UCT]: 2020-01-13 23:01:13 Age [y:d:h:m:s]: 05:137:14:51:18
Block: 45018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1248512 RingCT/type: yes/0
Extra: 010f6b3661069ae87274cef0b47887e1bb35b02194f07262ec88786d49a4bc5a3602110000000c4ac5aa02000000000000000000

1 output(s) for total of 435.348967122000 dcy

stealth address amount amount idx
00: 0a8b60d31274750096f0d6eb65f1ba8eb66dfe1819b0625e0cb5e0d89a4bc3c8 435.348967122000 82102 of 0

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": 45028, "vin": [ { "gen": { "height": 45018 } } ], "vout": [ { "amount": 435348967122, "target": { "key": "0a8b60d31274750096f0d6eb65f1ba8eb66dfe1819b0625e0cb5e0d89a4bc3c8" } } ], "extra": [ 1, 15, 107, 54, 97, 6, 154, 232, 114, 116, 206, 240, 180, 120, 135, 225, 187, 53, 176, 33, 148, 240, 114, 98, 236, 136, 120, 109, 73, 164, 188, 90, 54, 2, 17, 0, 0, 0, 12, 74, 197, 170, 2, 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